Skip to main content

The Relationship Between Hard Drives and Storage Pools

In a NAS **hard disks (physical storage media) **and **storage pools (logical storage abstraction layers) **are the core tiers that constitute a storage system. The two realize the conversion from physical resources to logical resources through specific Technology Implementation, and their relationship can be analyzed from the dimensions of "physical foundation" and "logical organization":

I. Hard Disk: The Physical Foundation of Storage Pools​

Hard disks (including HDD mechanical hard disks, SSD solid-state drives, etc.) are the underlying physical carriers of storage systems, with independent hardware attributes (such as capacity, rotational speed, interface protocol, etc.). A single hard disk can directly provide storage space as a "raw device", but limited by its physical characteristics (such as the upper limit of single-disk capacity, no fault tolerance, performance bottlenecks, etc.), it is difficult to meet the requirements of complex scenarios for reliability, scalability and performance.

In a storage system, the core role of hard drives is to provide raw physical capacity, and their quantity and specifications (such as capacity consistency) directly determine the potential scale and performance ceiling of the storage pool.

II. Storage Pool: A Logical Abstraction and Management Unit for Hard Disk Resources​

A storage pool is a logical storage container formed by aggregating and virtualizing multiple physical hard disks via a software layer. It masks the physical differences of underlying hard disks (such as brand and model), integrates the capacity of multiple hard disks into a unified, dynamically manageable resource pool, and its core functions include:

  • Capacity aggregation: Integrate the physical capacities of multiple hard drives into a continuous logical capacity, breaking through the capacity limit of a single drive;

  • Reliability Enhancement: Data redundancy is implemented at the hard disk level via RAID technologies (such as RAID 5/6/10) to improve the fault tolerance of the storage system;

  • Dynamic expansion: Supports adding new hard disks without interrupting services to expand the total capacity of the storage pool;

  • Performance optimization: Improve read and write efficiency through striping (e. g. RAID 0) or tiered storage (e. g. incorporating SSDs and HDDs into the same storage pool to achieve the separation of hot and cold data).

3. Hierarchical Relationship Between Hard Disks and Storage Pools​

The two present a progressive relationship of "physical layer → logical layer", which is specifically manifested as follows:

  • Dependencies: A storage pool must be built on at least one physical hard drive; no storage pool can exist without a hard drive. Conversely, a hard drive can be used independently of a storage pool (albeit with limited functionality).

  • Mapping relationship: The capacity of a storage pool is derived by subtracting the RAID redundancy overhead (such as parity information and mirror space) from the total capacity of the hard drives it contains, that is: Available storage pool capacity = Σ physical hard drive capacity - RAID redundancy capacity

  • Management Granularity: Hard disks serve as physical-level management units (e. g., for replacement, bad sector scanning), while storage pools function as logical-level management units (e. g., for volume creation, capacity allocation adjustment).

IV. Typical Application Process​

In a NAS system, the configuration process for hard drives and storage pools typically proceeds as follows:

  1. Physical hard drives are connected to the NAS (via interfaces such as SATA);

  2. The system identifies the hard disk and initializes it (e. g., formatting, health status check);

  3. The administrator adds the specified hard drives to the storage pool and selects the RAID level (which defines the redundancy and performance strategy);

  4. Once a storage pool is created, it can be further divided into "Volumes" or "shared folders" for users to store actual data.

5. Example Analogies​

The relationship between a hard disk and a storage pool can be analogized to that between a "bucket" and a "reservoir":

Imagine that you have several separate buckets, which are equivalent to hard disk drives. Each bucket has its own capacity, say 20 liters or 30 liters, but using them individually comes with many limitations: for instance, a small bucket cannot hold the amount of water that a large bucket can, if one bucket leaks (fails), all the water inside it is lost, and you can only scoop water from one bucket at a time, which is inefficient.

At this point, you come up with a solution: connect the bottoms of these buckets together with pipes to form a unified "reservoir"(equivalent to a storage pool). This reservoir is no longer limited by the capacity of a single bucket, but instead uses the total capacity of all buckets (minus the loss from the connecting pipes, similar to RAID redundancy).

When in use, you just draw water directly from the reservoir, without needing to care which bucket the water comes from; if a bucket leaks (a hard drive fails), the reservoir will automatically replenish the water from other buckets (RAID fault tolerance) without affecting normal use; when you buy new buckets (add new hard drives) later, just connect them to the pipeline, and the total capacity of the reservoir will increase (dynamic expansion).

Here, **the bucket (hard disk) is a physically existing "individual container" **that provides the raw "water-holding capacity";**the reservoir (storage pool) is a "logical container" formed by connection and integration **that turns scattered individual capabilities into unified, reliable, and easily manageable integrated resources.